Common problems

• AWeb won't start. It says it can't find xxx.image or xxx.gadget.
  Probably you haven't installed the latest ClassAct classes. You can find them on ftp://ftp.thule.no/pub/classact/.

• AWeb crashes when loading a GIF image
  The commonly used ZGif datatype version 39.16 had a bug. Be sure to use version 39.18 or better of the ZGif datatype, or another GIF datatype.

• When I try to print the document it just does nothing
  You probably try to print from a screen with more than 256 colours. Most printer drivers can't handle these kind of screens. You have to change your screen mode used first.
  You might want to use TurboPrint (latest version). AWeb will detect that TurboPrint is running, and will be able to print in more than 256 colours.

  Tip: Create a separate configuration (using the CONFIG tooltype or argument) with a 256 colour screen mode. When you like to print a page, first continue surfing, and after you have quit AWeb start it again with the other configuration. Now you can fetch the document from cache and print it off-line.

• AWeb doesn't display all of the page. Other browsers display the page correctly
  Probably the page contains some erroneous HTML. One of the common errors is the use of bad comments as a divider line in the HTML source. In tolerant HTML mode, AWeb tries to interpret the comment as it was probably meant by the author. In strict HTML mode, large parts of the page may be commented out because of the bad syntax.
  Try changing the HTML mode to tolerant or compatible.

• AWeb becomes terribly slow if I run it on its own screen.
  This has something to do with chip memory usage and DMA bandwidth. Apparently, the problem becomes worse when you have an accelerated machine.
  The solution is to use either a lower or a higher speed ("baudrate") to communicate with your modem. Start at the modem speed (so if you own a 14k4 modem, start at 14k4 communication speed). Then increase the speed until you find a dramatic slowdown. Then go one step back.
  Changing the communication speed with your modem might involve adapting the settings for your dialler, TCP stack and/or your SANA driver. Refer to the respective documentations.

• Backgrounds in AWeb are terribly slow, much slower than competitive Amiga browsers.
  This might be caused by an unsuited picture datatype. Use the 24-bit picture datatype only on CyberGraphics screens; on original Amiga screens this datatype becomes very slow. Use the original picture.datatype from your Workbench diskette.

• The colour requester from the program settings: Palette page messes things up on a CyberGraphics screen.
  This is caused by the palette-orientated design of the Amiga OS. This design works fine on Amiga chipset screens, but isn't really suited for graphics cards.

• I run AWeb on a small screen, and the save, use, test, cancel buttons in this settings window fall outside the screen.
  Start the ClassAct preference program, or if you run AWeb under OS 3.5 or higher, the Reaction preference program, then go to the "Misc" page, and set "layout spacing" to a lower number.

• Closing the AWeb public screen while there is a visitor window open crashes if the screen is a CyberGraphics screen.
  This is a bug in CyberGraphics V 2.15 and lower. The same thing happens on other CyberGraphics screens.

• If the window is not active, a click in the scroller container (outside the knob) moves the scroller but doesn't scroll the window contents.
  This is a bug in Intuition. The same thing happens sometimes with MultiView.

• I use MagicMenu, and every now and then my system hangs if I open a menu.
  With Magic Menu version 2.15 or higher this problem should be gone.

• I don't use MagicMenu, but my system hangs if I click on the wide part of the chooser gadget in the settings window.
  Be sure to use the version of chooser.gadget included in this archive.
  Also, some animated mouse pointer commodities are known to cause this hang.